Handle Disabled Procedures in Underlying Data Sources
This page last changed on Nov 28, 2008.
Oracle Data Service Integrator Documentation > Data Services Developer's Guide How To Handle Disabled Procedures in Underlying Data SourcesThis topic explains how to enable an update map for a logical data service when an underlying data source has disabled procedures. Check the Data SourcesIf a Create, Update, or Delete procedure is disabled in a data source that your logical data service uses, part of the update map is disabled as well. Specifically, the update block that maps to the data source is disabled. For example, you might have a physical data service that is missing a Create, Update, or Delete procedure. Physical Data Service with No Create or Delete ProcedureAs a result, the update block that maps to this data source has its Create and Delete procedures disabled. Update Block with Disabled Create and Delete ProceduresWhen you mouse over the disabled procedure icons, you see tooltips telling you that create and delete operations are not possible for the service. Resolve the Disabled ProceduresYou need to resolve the disabled procedures so that you can deploy the service to the server. To resolve them, you can:
The solution you choose depends on your needs. Disable the Update BlockIf you do not need to use the procedures that are disabled in the underlying data source, you can disable the entire update block:
Add or Enable Procedures in the Underlying Data SourceYou can also enable procedures in or add them to the underlying data source. For example, to add a procedure to a physical data service:
Change the XML Return TypeYou can also change the XML schema the logical data service uses for its return type. For example, you might remove the element that attempts to update the disabled data source. You can even do this dynamically from Workshop for WebLogic. To change the return type from Workshop for WebLogic:
See AlsoConceptsHow Tos
|
![]() |
Document generated by Confluence on Jan 13, 2009 15:57 |